Enhanced queue management for power control of data storage device

ABSTRACT

Systems, methods, and firmware for power control of data storage devices are provided herein. In one example, a data storage device is presented. The data storage device includes a transaction queue configured to enqueue storage operations received over a host interface of the data storage device for storage and retrieval of data on storage media. The data storage device includes a storage controller configured to process a power/current target to establish a dequeue process for storage operations in the transaction queue which operates the data storage device within the power/current target.

TECHNICAL BACKGROUND

Computer and network systems such as data storage systems, serversystems, cloud storage systems, personal computers, and workstations,typically include data storage devices for storing and retrieving data.These data storage devices can include hard disk drives (HDDs), solidstate storage drives (SSDs), tape storage devices, optical storagedrives, hybrid storage devices that include both rotating and solidstate data storage elements, and other mass storage devices.

As computer systems and networks grow in numbers and capability, thereis a need for ever increasing storage capacity. Data centers, cloudcomputing facilities, and other at-scale data processing systems havefurther increased the need for digital data storage systems capable oftransferring and holding immense amounts of data. Data centers can housethis large quantity of data storage devices in various rack-mounted andhigh-density storage configurations.

Data center operators typically attempt to maximize data centerutilization by including a high density of storage devices in a givenvolume. However, these higher densities lead to greater powerdissipation with associated heat generation and cooling problems. Powercapping has been employed in data centers to set maximum power usagesfor the various computing systems contained in the data centers.However, power dissipation by individual components of the computingsystems is limited to very coarse adjustments, such as sleep modes orpowering down of unused computing elements.

OVERVIEW

Systems, methods, and firmware for power control of data storage devicesare provided herein. In one example, a data storage device is presented.The data storage device includes a transaction queue configured toenqueue storage operations received over a host interface of the datastorage device for storage and retrieval of data on storage media. Thedata storage device includes a storage controller configured to processat least a power control instruction received over the host interface toestablish a dequeue process for storage operations in the transactionqueue which operates the data storage device within a power targetindicated by the power control instruction.

In another example, a method of operation a data storage devicecomprising storage media configured to store data for later retrieval ispresented. The method includes, in a transaction queue, queuing storageoperations that are received over a host interface of the data storagedevice for storage and retrieval of data on the storage media. Themethod includes, in a storage controller, processing at least a powercontrol instruction received over the host interface to establish adequeue process for storage operations in the transaction queue whichoperates the data storage device within a power target indicated by thepower control instruction.

In another example, a data storage device is presented. The data storagedevice includes rotating storage media configured to store data forlater retrieval using one or more read/write heads. The data storagedevice includes an input queue configured to enqueue storage operationsreceived over a host interface of the data storage device for storageand retrieval of data on the storage media. The data storage deviceincludes a storage processor configured to process at least a powercontrol instruction received over the host interface to establishdequeue sequencing for storage operations in the input queue whichoperates the data storage device within a power target indicated by thepower control instruction. The storage processor is configured toexecute the storage operations in accordance with the dequeue process.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a storage system.

FIG. 2 illustrates a method of operating a data storage device.

FIG. 3 illustrates a storage system.

FIG. 4 illustrates a method of operating a data storage system.

FIG. 5 illustrates a table relating power selections to queue depths.

FIG. 6 illustrates dequeue operations.

FIG. 7 illustrates a control system.

DETAILED DESCRIPTION

Data storage systems employ various mass-storage devices, such as harddisk drives, solid state drives, among other storage devices. However,these storage devices can use high levels of power which can lead toexcessive power consumption by data centers which aggregate many datastorage systems together. In the examples discussed below, variousmethods, systems, apparatuses, and firmware allow for fine-grainedcontrol of power consumption in the various mass storage devices used indata servers and data storage systems. For example, a hard disk drivecan be placed into a power capped mode which modifies parameters of thehard disk drive to allow storage operations to fall below a powerthreshold for that hard disk drive. Other examples of power capping andpower control of data storage devices are discussed below.

In a first example of an enhanced data storage system, FIG. 1 ispresented. FIG. 1 is a system diagram illustrating data system 100.System 100 includes data storage device 110 and host system 140. Datastorage device 110 and host system 140 communicate over storage link130. Data storage device 110 can be included in an assembly thatincludes one or more data storage devices and one or more controlsystems. In FIG. 1, data storage device 110 includes control system 112and storage media 114. Control system 112 is communicatively coupled tostorage media 114. Although control system 112 is shown as internal todata storage device 110 in this example, it should be understood that inother examples control system 112 can be included in other elementsexternal to data storage device 110. In some examples, data storagedevice 110 comprises a hard disk drive (HDD) with rotating magneticstorage media, or a hybrid disk drive which incorporates both rotatingand solid state storage media.

In operation, data storage device 110 receives read or write operationsover storage link 130 issued by host system 140. Responsive to readoperations, data storage device 110 can retrieve data stored uponstorage media 114 for transfer to host system 140. Responsive to writeoperations, data storage device 110 stores data on storage media 114.The storage operations are received by control system 112 over storagelink 130, and can be received into a transaction queue or input/outputoperations (IOs) queue, such as queue 111, for handling by controlsystem 112. It should be understood that other components of datastorage device 110 are omitted for clarity in FIG. 1, such as chassis,enclosures, fans, interconnect, read/write heads, armatures, preamps,transceivers, processors, amplifiers, motors, servos, enclosures, andother electrical and mechanical elements.

To further illustrate the operation of data system 100, FIG. 2 isprovided. FIG. 2 is a flow diagram illustrating a method of operatingdata storage device 110. The operations of FIG. 2 are referenced belowparenthetically. In FIG. 2, data storage device 110 enqueues (201)storage operations received over a host interface of data storage device110 for storage and retrieval of data on storage media 114. In thisexample, the storage operations can be transferred by host system 140over link 130 for handling by data storage device 110. These storageoperations, such as write or read operations, can be received by datastorage device into queue 111 for later handling by control system 112.In many examples, control system 112 includes a host interface forreceiving the storage operations and then control system 112 enqueuesthe storage operations into queue 111.

Data storage device 110 receives (202) a power control instruction overa host interface. In addition to storage operations, other instructionsand operations can be transferred by host system 140 for control andcommunication with data storage device 110. One such control instructioncan comprise a power control instruction and can indicate a desiredpower target comprising a power limit or current draw for data storagedevice 110. The power target can indicate that host system 140 instructsdata storage device 110 not exceed a maximum power dissipation, or for aspecified supply voltage not exceed a maximum current draw. These limitscan be indicated in watts (W) for power or amps (A) for current (with anaccompanying voltage (V) input indication when more than one voltageinput is associated with data storage device 110), although other unitscan be employed. In some examples, the power control instructionscomprise one or more T10 standard-compliant power managementinstructions.

It should be noted that instead of, or in combination with, receivingthe power control instruction over the host interface, data storagedevice 110 can have internally-defined power or current targets. Forexample, a default power target or current target can be established indata storage device 110 during manufacturing or initial firmwareinstallation. In other examples, a current target or power target can bereceived during manufacturing or initial firmware installation and thendata storage device 110 can employ this power target or current targetduring operations. Later, a change in the power target or current targetcan be received over a host interface and employed as described hereinby data storage device 110.

Data storage device 110 processes (203) the power control instruction toestablish a dequeue process for storage operations in queue 111 whichoperates the data storage device within a power target indicated by thepower control instruction. Over time, many storage operations, such aswrite operations and read operations, can be received and held in queue111. These storage operations are many times handled in the order inwhich received, as in a first-in, first-out (FIFO) scheme. However, thepower consumed by data storage device 110 in handling these storageoperations in a FIFO manner can lead to higher than desired powerdissipation or current draw. Thus, control system 112 establishes adequeue process or dequeue sequence which alters a power dissipation orcurrent draw of data storage device 110 to comply with the power targetindicated in the power control instruction.

Several factors can influence the power or current associated with adequeue process, such as a depth of queue 111, power dissipation ofindividual components of data storage device 110, and properties of thestorage operations themselves. The depth of queue 111 can vary based onqueue depth instructions from host system 140, or by queue depthalterations made by control system 112, which are limited by associatedminimum and maximum sizes allowed for queue 111. Power dissipation ofthe individual components of data storage device 110 can vary due tovariations in properties of the electromechanical elements which moveread/write (R/W) head components, armatures, servos, motors, and thelike. Each storage operation can also have different associated powerconsumption, based in part on a storage address, a read or writecommand, and what storage operations are performed prior to andsubsequent to a current storage operation.

Control system 112 can minimize power dissipation by selecting a currentstorage operation from queue 111 based on a previous storage operationselected from queue 111. In rotating magnetic media examples, R/W headsmust be positioned over the storage media to read and write data on themedia. A first storage operation can be directed to a first storagelocation on the media, and a second storage operation can be directed toa second storage location on the media distant from the first storagelocation. Electromechanical components used to move the R/W heads canexperience an increased power dissipation or current draw when these twostorage locations are more distant from each other or require largechanges in movement of the R/W heads from a present location.

Control system 112 can select storage operations from queue 111 forexecution by control system 112, such as reading of data from media 114or writing data to media 114. However, intelligent selection of storageoperations from queue 111 can add to latency delays in execution of thestorage operations. Additionally, data coherency must be maintained sothat certain read or write operations occur in a proper order to preventoverwriting of data being read or reading of incorrect or stale data,among other issues. Control system 112 can establish a search process orsearch effort for selecting storage operations to dequeue from queue111. This search effort can vary based on the factors above, such as apresent queue depth.

In some examples, a table or other data structure can be establishedwhich relates queue depths of queue 111 to estimated power levels ofdata storage device 110. When a power control instruction is received,control system 112 can select an entry from the table which correspondsto a present queue depth of queue 111 and an estimated power levelcorresponding to the power target indicated by the power controlinstruction. The selected entry indicates a dequeue sequence weightingfactor. This dequeue sequence weighting factor can relate to a R/W headseek distance threshold for selecting next storage operations to dequeuefrom queue 111. In some examples, the selected entry relates to anestimated access time (EAT) weighting factor, where EAT is a rotationalposition metric related to a time delay needed to complete a seekoperation of commands in queue 111. Control system 112 can be configuredto select the EAT weighting factor from a table relating transactionqueue depths and estimated power levels, and employ the EAT weightingfactor to select ones of the storage operations from queue 111 duringthe dequeue process.

Control system 112 can then execute the storage operations, such as byperforming read or write operations, as each storage operation isdequeued from queue 111 according to the dequeue process. During thehandling of the dequeued storage operations, power monitor 113 monitorspower dissipation or current draw of data storage device 110. If anactual power or current draw is above a limit indicated by the powercontrol instruction, then adjustments can be made to the dequeueprocess, such as by selecting a different estimated power level for thepresent queue depth from the table indicated above. A specific exampleof a table relating queue depth to incremental power levels is discussedin FIG. 5.

Returning to the elements of FIG. 1, data storage device 110 includesone or more computer readable storage media 114 accessible via one ormore read/write heads and associated electromechanical elements. Datastorage device 110 includes power monitor 113 for measuring current drawor power consumption of data storage device. Queue 111 can comprise oneor more data storage media which can include a data structure forholding storage operations prior to execution by control system 112.Data storage device 110 also includes processing circuitry,communication interfaces, armatures, preamps, transceivers, processors,amplifiers, motors, servos, enclosures, and other electrical andmechanical elements. Data storage device 110 can also comprise cachesystems, chassis, enclosures, fans, interconnect, cabling, or othercircuitry and equipment.

Data storage device 110 can comprise a hard disk drive, hybrid diskdrive, or other computer readable storage device. Data storage device110 can include further elements, such as those discussed for hard diskdrives 310 in FIG. 3, although variations are possible. The computerreadable storage media of data storage device 110 can include rotatingmagnetic storage media, but can additionally include other media, suchas solid state queues or cache systems of data storage device 110. Theseother media can include solid state storage media, optical storagemedia, non-rotating magnetic media, phase change magnetic media,spin-based storage media, or other storage media, includingcombinations, variations, and improvements thereof. In some examples,data storage device 110 comprises a hybrid hard drive employing solidstate storage elements in addition to rotating magnetic storage media.Storage media 114 can employ various magnetic storage schemes, such asshingled magnetic recording (SMR), non-shingled magnetic recording,perpendicular magnetic recording (PMR), including combinations,variations, and improvements thereof.

Storage control system 112 includes processing circuitry, communicationinterfaces, and one or more non-transitory computer-readable storagedevices. The processing circuitry can comprise one or moremicroprocessors and other circuitry that retrieves and executes firmwarefrom memory for operating as discussed herein. The processing circuitrycan be implemented within a single processing device but can also bedistributed across multiple processing devices or sub-systems thatcooperate in executing program instructions. Examples of the processingcircuitry include general purpose central processing units, applicationspecific processors, and logic devices, as well as any other type ofprocessing device, combinations, or variations thereof. Thecommunication interfaces can include one or more storage interfaces forcommunicating with host systems, networks, and the like. Thecommunication systems can include transceivers, interface circuitry,connectors, buffers, microcontrollers, and other interface equipment.

Host system 140 can include processing elements, data transfer elements,and user interface elements. In some examples host system 140 is acentral processing unit of a computing device or computing system. Inother examples, host system 140 also includes memory elements, datastorage and transfer elements, controller elements, logic elements,firmware, execution elements, and other processing system components. Inyet other examples, host system 140 comprises a RAID controllerprocessor or storage system central processor, such as a microprocessor,microcontroller, Field Programmable Gate Array (FPGA), or otherprocessing and logic device, including combinations thereof. Host system140 can include, or interface with, user interface elements which canallow a user of data storage system 100 to control the operations ofdata storage system 100 or to monitor the status or operations of datastorage system 100. These user interface elements can include graphicalor text displays, indicator lights, network interfaces, web interfaces,software interfaces, user input devices, or other user interfaceelements. Host system 140 can also include interface circuitry andelements for handling communications over storage link 130, such aslogic, processing portions, buffers, transceivers, and the like.

Storage link 130 can include one or more serial or parallel data links,such as a Peripheral Component Interconnect Express (PCIe) interface,serial ATA interface, Serial Attached Small Computer System (SAS)interface, Integrated Drive Electronics (IDE) interface, ATA interface,Universal Serial Bus (USB) interface, wireless interface, Direct MediaInterface (DMI), Ethernet interface, networking interface, or othercommunication and data interface, including combinations, variations,and improvements thereof. Although one bus 130 is shown in FIG. 1, itshould be understood that one or more discrete links can be employedbetween the elements of data storage system 100.

As a further example data storage system employing a data storage array,FIG. 3 is presented. FIG. 3 is a system diagram illustrating datastorage system 300. Data storage system 300 includes one or more harddisk drives (HDDs), such as HDD 310, and also includes one or more hostsystems 340. HDD 310 and host system 340 communicate over storage link330. Various elements of HDD 310 can be included in data storage device110 of FIG. 1, although variations are possible. Although one HDD isfocused on in FIG. 3, it should be understood that more than one HDDcould be included and linked to host system 340 or other host systems,such as in a data storage environment employing many hard disk drives inan array.

HDD 310 comprises a hard disk drive, hybrid disk drive, or othercomputer readable storage device. HDD 310 includes queue 311, storagecontroller 312, read/write (R/W) heads 313, storage media 314,voltage/current sense circuit 315, and power monitor 316. Storagecontroller 312 includes one or more power selection tables 320. HDD 310can include further elements, such as armatures, preamps, transceivers,processors, amplifiers, motors, servos, enclosures, and other electricaland mechanical elements.

Storage controller 312 handles storage operations for HDD 310, such asreceiving write storage operations 331 and read storage operations 332from host system 340 over storage link 330. Write data can be receivedwith the associated write operations for storage on storage media 314,and read data 333 can be provided to hosts responsive to one or moreread operations. Storage controller 312 or host system 340 can establishany number of logical volumes or logical storage units for HDD 310 oramong other HDDs, which can comprise spanning, redundant arrays,striping, or other data storage techniques. Queue 311 comprisescomputer-readable storage media which can be included in elements ofstorage controller 312 as one or more data structures. Storagecontroller 312 comprises one or more processing systems, such as amicroprocessor and associated computer-readable storage media andcommunication interfaces.

HDD 310 can be included in a redundant array of independent disks (RAID)array, a JBOD device (“Just a Bunch Of Disks”), or a VBOD device(“Virtual Bunch of Disks”) which include a plurality of independentdisks which can be spanned and presented as one or more logical drivesto host system 340. A VBOD device employs one or more shingled magneticrecording (SMR) hard disk drives in an array. However, SMR diskstypically have inefficiencies for random writes due to the shinglednature of adjacent tracks for data. The VBOD abstracts the SMR drivesand allows random writes and random reads while still having underlyingSMR media which ultimately hold the associated data.

Storage link 330 can include one or more links, although a single linkis shown in FIG. 3. Storage link 330 can comprise a storage or diskinterface, such as Serial Attached ATA (SATA), Serial Attached SCSI(SAS), FibreChannel, Universal Serial Bus (USB), SCSI, InfiniBand,Peripheral Component Interconnect Express (PCIe), Ethernet, InternetProtocol (IP), or other parallel or serial storage or peripheralinterfaces, including variations and combinations thereof.

Host system 340 can include one or more computing and network systems,such as personal computers, servers, cloud storage systems, packetnetworks, management systems, or other computer and network systems,including combinations and variations thereof. In operation, host system340 issues read and write commands or operations to HDD 310 over storagelink 330, among other commands or operations which can include controlinstructions, metadata retrieval operations, configuration instructions,and the like. Likewise, HDD 310 can transfer read data over storage link330, among other information such as graphical user interfaceinformation, status information, operational information, failurenotifications, alerts, and the like.

To further illustrate the operation of system 300 and HDD 310, FIG. 4 ispresented. FIG. 4 is a sequence diagram illustrating a method ofoperation of system 300. In FIG. 4, HDD 310 can receive various read andwrite operations from host system 340 for reading and writing data onstorage media 314. During these operations, host system 340 might desireto adjust a power cap or power limit for HDD 310, such as when HDD 310is in a storage array with many HDDs and power limits are desired forthe entire array or associated data storage center.

Pursuant to this, host system 340 can transfer one or more power controlinstructions to HDD 310, such as power limit instruction 391 or currentlimit instruction 390. These power control instructions can comprisecommands which are interpreted by HDD 310 as imposing a limit or targetpower consumption for HDD 310. In some examples, the power controlinstructions are included in a standardized command set, such as relatedto power management interfaces or T10 power management controlstandards. These power control instructions can indicate power targetsor power limits for HDD 310, and can be indicated in a power level(watts) or a current level (amps) for a specific supply voltage. In manyexamples, HDD 310 can have multiple supply voltages, such as 12 VDC forelectromechanical elements (including motors, servos, armatureelements), and 5 VDC for logic and processing elements (includingmicroprocessors, queues, host interfaces). A current limit or targetcurrent can be specified by host system 340 for any of the voltages usedby HDD 310. Alternatively, a total power consumption or powerconsumption per supply voltage can be specified.

To meet the power targets or power limits indicated in the power controlinstructions, storage controller 312 can modify operation of HDD 310.Specifically, storage controller 312 modifies dequeue processes forstorage operations that have been queued into queue 311 after receiptfrom host system 340. These storage operations can include readoperations or write operations, among other operations, such astraversal operations, metadata operations, and other command/controloperations, including combinations thereof. These storage operations aremany times handled in the order in which received, as in a FIFO scheme.However, the power consumed by HDD 310 in handling these storageoperations in a FIFO manner can lead to higher than desired powerdissipation or current draw. Thus, storage controller 312 establishes adequeue process or dequeue sequence which alters a power dissipation orcurrent draw of HDD 310 to comply with the power target indicated in thepower control instruction.

In rotating magnetic media storage drives, such as HDD 310, the power orcurrent associated with executing storage operations can vary based onthe movement of electromechanical elements used to position R/W headsover the associated media. In HDD 310, R/W heads 313 are moved over thesurfaces of media 314 using associated armatures, voicecoil actuators,or servos and the like. Movements of the R/W heads 313 can be associatedwith different power dissipations, and can vary based on distance ofmovement, speed of movement, change in direction, or other factors.These movements are influenced by storage addresses of each storageoperation, which indicates where on media 314 that R/W heads are to bepositioned. Storage controller 312 can thus alter power dissipations ofHDD 310 by carefully selecting storage operations from queue 311 basedon predicted movement of R/W heads 313 and predicted power dissipationfor those selected storage operations.

To select each storage operation from queue 311, a search effort isapplied to queue 311 by storage controller 312. This search effort canbe employed to minimize movement of R/W heads 313 from storage operationto storage operation. However, intelligent selection of storageoperations from queue 311 can add to processing delays and latencydelays in execution of the storage operations. Additionally, datacoherency must be maintained so that certain read or write operationsoccur in a proper order to prevent overwriting of data being read orreading of incorrect or stale data, among other issues.

In this example, power selection table 320 is employed as a look-uptable to enhance the establishment of a dequeue process. FIG. 5 showstable 500 as an example of power selection table 320, althoughvariations are possible. In FIG. 5, columns indicate present queuedepths and rows indicate incremental estimated power levels, andselections can be made for particular estimated access time (EAT)weighting factors. The queue depth can vary during operation due tochanges in a queue depth made by storage controller 312 or instructionsby host system 340. Typically, a queue depth is selected to be a fixedvalue during operation of a data storage device, but may vary dependingupon the types of storage operations handled by the data storage device.For example, a HDD tailored to handling sequential write operationsmight have a different queue depth than a HDD tailored to handlingrandom read/write operations. Other variations are possible. Theestimated power level corresponds to different estimated powerconsumptions by the associated HDD, and can be incremented in varioussteps or resolutions, such as 50 milliwatts (mW) or 100 mW, among othersteps. Although each incremental estimated power level does not have aspecific or actual power consumption value determined in FIG. 5, eachincreasing incremental power level will have an increased associatedpower consumption.

Relating the elements of FIG. 5 to the operation of elements in FIG. 3,storage controller 312 selects an initial entry from table 500 whichcorresponds to a present queue depth employed for queue 311 and adesired power target or power limit indicated in the power controlinstruction. This initial selection might be for “first EAT” factor inFIG. 5, which corresponds to a queue depth of 16 storage operations andan incremental power level of 8.

However, during operation of HDD 310, power is monitored by powermonitor 316 and voltage/current sense 315, and if the present powerconsumption remains above the power target or power limit, then a lowerincremental power level can be selected. For example, the first EATweighting factor selection might provide too high of a power consumptionfor HDD 310, and thus storage controller 312 selects another lowerincremental power level for the same queue depth, such as “second EAT”factor which corresponds in FIG. 5 to a queue depth of 16 and anincremental power level of 2. If the power consumption then drops belowthe desired level, then HDD 310 can be operated using the second EATweighting factor. Further refinements can be made to fine tune the powerconsumption to be under the power limit or power target but stillprovide for the highest acceptable incremental power level. AlthoughFIG. 5 shows a 40 row table for queue sizes of 1 to 128, it should beunderstood that other table sizes and granularities can be provided.Moreover, instead of a table, a formulaic selection can be establishedusing the queue depth and incremental power level as inputs to a powerequation which outputs an EAT weighting factor.

The selected EAT weighting factor entry of table 500 indicates a dequeuesequence weighting factor. The EAT weighting factor can comprise aparameter or constant which corresponds to a weighting factor for R/Whead seek distances considered when each storage operation is selectedfor execution from queue 311. The estimated access time, or EAT, is arotational position metric related to a time delay needed to complete aseek operation of commands in queue 311. Storage controller 312 can beconfigured to select the EAT weighting factor from table 500 relatingtransaction queue depths and estimated power levels, and employ the EATweighting factor to select ones of the storage operations from queue 311during the dequeue process.

Storage controller 312 can then execute the storage operations, such asby performing read or write operations on media 314 with R/W heads 313,as each storage operation is dequeued from queue 311 according to thedequeue process. During the handling of the dequeued storage operations,power monitor 316 monitors power dissipation or current draw of HDD 310,such as by monitoring current draw in voltage/current sense circuitry315 for each of the +5 VDC and +12 VDC supply powers. If an actualmeasured power or current draw is above a limit indicated by the powercontrol instruction, then adjustments can be made to the dequeueprocess, such as by selecting a different incremental power level row intable 500 for the present queue depth, which indicates a different EATweighting factor. Specifically, storage controller 312 can be configuredto process power usage measured during the dequeue process against thepower target to identify a power delta, and adjust the EAT weightingfactor based at least on the power delta. The EAT weighting factor canbe adjusted by selecting a lower incremental power level in a table,such as indicated in FIG. 5.

To further illustrate the effect of the selected EAT weighting factor onthe dequeue process, FIG. 6 is presented. FIG. 6 includes two operatingmodes a dequeue process for a data storage device, with a firstoperating mode 601 indicating a higher power dequeue process than secondoperating mode 602. For this example, the data storage device is harddisk drive, and a queue depth of 10 is shown, although other depths canbe employed. Though not shown in FIG. 6, hard disk drives typicallyinclude a voicecoil actuator or servo for moving an armature that holdsthe read/write heads. The servo/armature mechanism consumes power whenpositioning the read/write heads across storage media surfaces todifferent angular positions. FIG. 3 shows an example of HDD 310 with R/Wheads 313 positioned over storage media 314.

In mode 601 of FIG. 6, a first EAT weighting factor is employed whichcorresponds to a higher power consumption by the associated HDD. In mode602 of FIG. 6, a second EAT weighting factor is employed whichcorresponds to a lower power consumption by the associated HDD. The EATweighting factor indicates a threshold in how much of a seek distance isdesired between each selected storage operation that is dequeued fromthe queue. The EAT, or estimated access time, typically corresponds to adistance that associated R/W heads need to be moved over a storagemedia, although time delays can accrue from other activity of a R/W headas well.

A search through a queue to find a next storage operation that minimizessuccessive movement of R/W heads can correspond to less powerconsumption, on average. A search through the queue to find a nextstorage operation that minimizes a host latency can correspond to morepower consumption, on average. A non-search process might comprise aFIFO process which has no regard for R/W head positioning and merelyselects based when a storage operation was queued. A most-aggressivesearch would always search the entire queue for a storage operationwhich minimizes the time delay or movement of R/W heads. However, abalanced approach is taken in the examples herein which allows a HDD tokeep power consumption below a specified target while maintainingperformance at acceptable levels without undue processing effort orlatency/delays to find next storage operations to dequeue and execute.

Turning now to mode 601, a first search effort is employed for selectingstorage operations to execute from queue 611. Mode 601 corresponds to afirst EAT weighting factor. In mode 601, a dequeue sequence ofA-B-C-D-E-F is performed. This dequeue sequence leads to large R/Wmovement distances (and associated times) between each storageoperation. Thus, mode 601 corresponds to a first power consumption forthe associated HDD.

In contrast, mode 602 shows an example using the same queued storageoperations as mode 601, but using a different search effort than in mode601, corresponding to a second EAT weighting factor. In mode 602, adequeue sequence of A-C-E-D-B-F is performed. This dequeue sequenceleads to smaller R/W movement distances (and associated times) betweeneach storage operation. Thus, mode 602 corresponds to a second powerconsumption for the associated HDD which is lower than the first powerconsumption of mode 601.

A more aggressive selection of storage operations, as indicated by thesecond EAT weighting factor in FIG. 6, can lead to a sequence of storageoperations which minimizes time/distance for R/W head positioning. Infurther examples, a storage controller can be configured to processpower usage measured during a current dequeue process that uses a firstEAT weighting factor against a power target to identify a power delta.When the power delta indicates the power usage is greater than the powertarget, the storage controller can be configured to determine second EATweighting factor for the dequeue process to dequeue storage operationsfrom the queue to reduce the power usage to below the power target.

In a further example, all entries in queue 611 can be considered for thenext storage operation selected, but a time threshold can be establishedusing the EAT weighting factor. This time threshold can lead toselection of the next storage operation from the queue as correspondingto R/W head movement delay from a current R/W head position that is lessthan the time threshold. However, when more than one entry in the queuemeets this time criteria, then further thresholds can be employed, suchas the first entry encountered which meets the time criteria or theentry with the least amount of time delay.

Advantageously, in the examples herein, various power-controlledoperations can be established for data storage devices, such as HDDs.Processing resources of associated storage controller or control systemscan be handled more efficiently by selecting storage operations fromassociated queues to meet power limits while maintaining sufficientperformance. Lookup tables can be employed to further speed up dequeueprocesses by quickly establishing EAT weighting factors, or otherdequeue weighting factors. These factors can allow efficient movement ofR/W heads and associated electromechanical components to maintainoperation within power targets indicated by a host system.

FIG. 7 is a block diagram illustrating control system 710. Controlsystem 710 handles storage operations for a storage assembly. Controlsystem 710 can be an example of control system 112 of FIG. 1, storagecontroller 312 of FIG. 3, or included in elements of host system 340 ofFIG. 3, although variations are possible. When control system 710 isincluded in a data storage drive, control system 710 receives storageoperations from host systems over storage link 760 by host interface 711into queue 716. Write data can be received in one or more writeoperations, and read data can be provided to hosts responsive to one ormore read operations.

Control system 710 includes host interface (I/F) 711, processingcircuitry 712, drive controller 713, storage system 714, queue 716, andpower monitor 717. Furthermore, control system 710 includes firmware 715which includes power selection table 721, power monitor module 722,dequeue process module 723 which, when executed by at least processingcircuitry 712, operates as described below.

Host interface 711 includes one or more storage interfaces forcommunicating with host systems, networks, and the like over at leastlink 760. Host interface 711 can comprise transceivers, interfacecircuitry, connectors, buffers, microcontrollers, and other interfaceequipment. Host interface 711 can also receive storage operations overlink 760 and place the storage operations into one or more I/O queues,such as queue 716, which buffer these storage operations for handling byprocessing circuitry 712. Link 760 can include one or more Ethernetinterfaces, SATA interfaces, SAS interfaces, FibreChannel interfaces,USB interfaces, SCSI interfaces, InfiniBand interfaces, NVMe interfaces,or IP interfaces, which allows for the host system to access the storagecapacity of HDD assembly.

Processing circuitry 712 can comprise one or more microprocessors andother circuitry that retrieves and executes firmware 715 from storagesystem 714. Processing circuitry 712 can be implemented within a singleprocessing device but can also be distributed across multiple processingdevices or sub-systems that cooperate in executing program instructions.Examples of processing circuitry 712 include general purpose centralprocessing units, application specific processors, and logic devices, aswell as any other type of processing device, combinations, or variationsthereof. In some examples, processing circuitry 712 includes asystem-on-a-chip device or microprocessor device, such as an Intel Atomprocessor, MIPS microprocessor, and the like.

Drive controller 713 can include one or more drive control circuits andprocessors which can control various data media handling among thevarious storage media of a storage device. Drive controller 713 alsoincludes storage interfaces 761, to couple to the various data storagemedia. In some examples, drive controller 713 handles management of aparticular recording technology, such as flash, optical, shingledmagnetic recording (SMR), perpendicular magnetic recording (PMR), heatassisted magnetic recording (HAMR), solid state media such as flashmedia, or other recording technology. As mentioned herein, elements andfunctions of drive controller 713 can be integrated with processingcircuitry 313.

Queue 716 can comprise any data structure included on a non-transitorycomputer readable storage media readable by processing circuitry 712 ordrive controller 713 and capable of storing storage operations andassociated data prior to handling by processing circuitry 712 or drivecontroller 713. Queue 716 can be implemented in a single storage devicebut can also be implemented across multiple storage devices orsub-systems co-located or distributed relative to each other. Hardwareelements associated with queue 716 can comprise additional elements,such as a controller, capable of communicating with processing circuitry712 or drive controller 713. Examples of storage media of queue 716include random access memory, read only memory, magnetic disks, opticaldisks, flash memory, SSDs, phase change memory, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand that can be accessed by an instruction execution system, as well asany combination or variation thereof, or any other type of storagemedia.

Power monitor 717 can comprise one or more sensing elements formeasuring power consumption, current draw, voltage levels, or otherassociated power related properties of a storage device associated withcontrol system 710, such as current draws or power dissipations. Powermonitor 717 can comprise current sensing elements, voltage sensingelements, power consumption processing elements, or other power sensingelements. Current sensing elements can include current sense resistors,operational amplifiers, comparators, magnetic current sensing elements,Hall Effect sensing elements, or other current sensing elements. Voltagesensing elements can include voltage dividers, operational amplifiers,or other analog or digital voltage sensing elements. Power monitor 717can also include various interfaces for communicating measured powerinformation, such as to processing circuitry 712. These interfaces caninclude transceivers, analog-to-digital conversion elements, amplifiers,filters, signal processors, among other elements. In some examples,power monitor 717 can each include microcontroller elements to controlthe operations of power monitor 717. In further examples, power monitor717 includes one or more control or communication interfaces forcommunicating with external current or power sensing elements.

Storage system 714 can comprise any non-transitory computer readablestorage media readable by processing circuitry 712 or drive controller713 and capable of storing firmware 715. Storage system 714 can includevolatile and nonvolatile, removable and non-removable media implementedin any method or technology for storage of information, such as computerreadable instructions, data structures, program modules, or other data.In addition to storage media, in some implementations storage system 714can also include communication media over which firmware 715 can becommunicated. Storage system 714 can be implemented as a single storagedevice but can also be implemented across multiple storage devices orsub-systems co-located or distributed relative to each other. Storagesystem 714 can comprise additional elements, such as a controller,capable of communicating with processing circuitry 712. Examples ofstorage media of storage system 714 include random access memory, readonly memory, magnetic disks, optical disks, flash memory, SSDs, phasechange memory, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or any other medium which can be usedto store the desired information and that can be accessed by aninstruction execution system, as well as any combination or variationthereof, or any other type of storage media.

Firmware 715 can be implemented in program instructions and among otherfunctions can, when executed by control system 710 in general orprocessing circuitry 712 in particular, direct control system 710 orprocessing circuitry 712 to operate data storage systems as describedherein. Firmware 715 can include additional processes, programs, orcomponents, such as operating system software, database software, orapplication software. Firmware 715 can also comprise software or someother form of machine-readable processing instructions executable byprocessing circuitry 712.

In at least one implementation, the program instructions can includefirst program instructions that direct control system 710 to monitorpower consumption of a data storage device associated with controlsystem 710 (power monitor module 722), determine when power consumptionis above a target power or current level, select a dequeue weightingfactor based on a power target (dequeue process module 723) using atleast power selection table 721 which relates queue depths toincremental power levels, and use the dequeue weighting factor to selectones of enqueued storage operations for execution (dequeue processmodule 723), among other operations.

In general, firmware 715 can, when loaded into processing circuitry 712and executed, transform processing circuitry 712 overall from ageneral-purpose computing system into a special-purpose computing systemcustomized to operate as described herein. Encoding firmware 715 onstorage system 714 can transform the physical structure of storagesystem 714. The specific transformation of the physical structure candepend on various factors in different implementations of thisdescription. Examples of such factors can include, but are not limitedto the technology used to implement the storage media of storage system714 and whether the computer-storage media are characterized as primaryor secondary storage. For example, if the computer-storage media areimplemented as semiconductor-based memory, firmware 715 can transformthe physical state of the semiconductor memory when the program isencoded therein. For example, firmware 715 can transform the state oftransistors, capacitors, or other discrete circuit elements constitutingthe semiconductor memory. A similar transformation can occur withrespect to magnetic or optical media. Other transformations of physicalmedia are possible without departing from the scope of the presentdescription, with the foregoing examples provided only to facilitatethis discussion.

The included descriptions and figures depict specific embodiments toteach those skilled in the art how to make and use the best mode. Forthe purpose of teaching inventive principles, some conventional aspectshave been simplified or omitted. Those skilled in the art willappreciate variations from these embodiments that fall within the scopeof the invention. Those skilled in the art will also appreciate that thefeatures described above can be combined in various ways to formmultiple embodiments. As a result, the invention is not limited to thespecific embodiments described above, but only by the claims and theirequivalents.

1. A data storage device, comprising: storage media configured to storedata for later retrieval; a transaction queue configured to enqueuestorage operations received over a host interface of the data storagedevice for storage and retrieval of data on the storage media; and astorage controller configured to: process at least a power controlinstruction received over the host interface to establish a dequeueprocess for storage operations in the transaction queue which operatesthe data storage device within a power target indicated by the powercontrol instruction; and determine an estimated access time (EAT)weighting factor for the dequeue process based at least on a presenttransaction queue depth and the power target.
 2. (canceled)
 3. The datastorage device of claim 1, wherein the storage controller is furtherconfigured to process power usage measured during the dequeue processagainst the power target to identify a power delta, and adjust the EATweighting factor based at least on the power delta.
 4. The data storagedevice of claim 1, wherein the storage controller is further configuredto select the EAT weighting factor from a table relating transactionqueue depths and estimated power levels and employ the EAT weightingfactor to select the storage operations from the transaction queueduring the dequeue process.
 5. The data storage device of claim 1,wherein the storage controller is further configured to process powerusage measured during the dequeue process against the power target toidentify a power delta; when the power delta indicates the power usageis greater than the power target, the storage controller configured toidentify a different EAT weighting factor that reduces the power usageto below the power target for further dequeue processes from a datastructure relating estimated power levels to transaction queue depths.6. The data storage device of claim 1, further comprising: a powermonitor configured to measure power usage by the data storage deviceduring at least the storage operations; and wherein the storagecontroller is further configured to process the power usage against thepower target to adjust dequeue sequencing for the transaction queue toalter read/write head seek behavior of the data storage device andreduce the power usage to within the power target.
 7. The data storagedevice of claim 1, wherein the power control instruction comprises alimit on at least one of a power dissipation or current draw for thedata storage device.
 8. The data storage device of claim 1, wherein thepower target is indicated as a desired current for a specified supplyvoltage of the data storage device.
 9. The data storage device of claim1, wherein the storage controller is further configured to execute thestorage operations in accordance with the dequeue process.
 10. A methodof operation a data storage device comprising storage media configuredto store data for later retrieval, the method comprising: in atransaction queue, queuing storage operations that are received over ahost interface of the data storage device for storage and retrieval ofdata on the storage media; in a storage controller, processing at leasta power control instruction received over the host interface toestablish a dequeue process for storage operations in the transactionqueue which operates the data storage device within a power targetindicated by the power control instruction; and in the storagecontroller, determining an estimated access time (EAT) weighting factorfor the dequeue process based at least on a present transaction queuedepth and the power target.
 11. (canceled)
 12. The method of claim 10,further comprising: in the storage controller, processing power usagemeasured during the dequeue process against the power target to identifya power delta, and adjusting the EAT weighting factor based at least onthe power delta.
 13. The method of claim 10, further comprising: in thestorage controller, selecting the EAT weighting factor from a tablerelating transaction queue depths and estimated power levels andemploying the EAT weighting factor to select the storage operations fromthe transaction queue during the dequeue process.
 14. The method ofclaim 10, further comprising: in the storage controller, processingpower usage measured during the dequeue process against the power targetto identify a power delta; when the power delta indicates the powerusage is greater than the power target, in the storage controller,identifying a different estimated access time (EAT) weighting factorthat reduces the power usage to below the power target for furtherdequeue processes from a data structure relating estimated power levelsto transaction queue depths.
 15. The method of claim 10, furthercomprising: in a power monitor, measuring power usage by the datastorage device during storage operations; in the storage controller,processing the power usage against the power target to adjust dequeuesequencing for the transaction queue to alter read/write head seekbehavior of the data storage device and reduce the power usage to withinthe power target.
 16. The method of claim 10, wherein the power controlinstruction comprises a limit on at least one of a power dissipation orcurrent draw for the data storage device.
 17. The method of claim 10,wherein the power target is indicated as a desired current for aspecified supply voltage of the data storage device.
 18. The method ofclaim 10, further comprising: executing the storage operations inaccordance with the dequeue process.
 19. A data storage device,comprising: rotating storage media configured to store data for laterretrieval using one or more read/write heads; an input queue configuredto enqueue storage operations received over a host interface of the datastorage device for storage and retrieval of data on the storage media; apower monitor configured to measure power usage by the data storagedevice during the storage operations; a storage processor configured to:process at least a power target to establish dequeue sequencing forstorage operations in the input queue which operates the data storagedevice within the power target; execute the storage operations inaccordance with the dequeue sequencing; and process the power usageagainst the power target to adjust the dequeue sequencing for the inputqueue to alter seek behavior of the one or more read/write heads of thedata storage device and reduce the power usage to within the powertarget.
 20. (canceled)
 21. A data storage device, comprising: storagemedia configured to store data for later retrieval; a transaction queueconfigured to enqueue storage operations received over a host interfaceof the data storage device for storage and retrieval of data on thestorage media; and a storage controller configured to: process at leasta power control instruction received over the host interface toestablish a dequeue process for storage operations in the transactionqueue which operates the data storage device within a power targetindicated by the power control instruction; process power usage measuredduring the dequeue process against the power target to identify a powerdelta; and based at least on the power delta indicating the power usageis greater than the power target, identify a different estimated accesstime (EAT) weighting factor that reduces the power usage to below thepower target for further dequeue processes from a data structurerelating estimated power levels to transaction queue depths
 22. A datastorage device, comprising: storage media configured to store data forlater retrieval; a transaction queue configured to enqueue storageoperations received over a host interface of the data storage device forstorage and retrieval of data on the storage media; a power monitorconfigured to measure power usage by the data storage device during atleast the storage operations; and a storage controller configured to:process at least a power control instruction received over the hostinterface to establish a dequeue process for storage operations in thetransaction queue which operates the data storage device within a powertarget indicated by the power control instruction; and process the powerusage against the power target to adjust dequeue sequencing for thetransaction queue to alter read/write head seek behavior of the datastorage device and reduce the power usage to within the power target.